FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.7.16  |  FHIR Version n/a  User: [n/a]

Resource ValueSet/FHIR Server from package nhsd.assets.stu3#1.7.0 (46 ms)

Package nhsd.assets.stu3
Type ValueSet
Id Id
FHIR Version R3
Source https://simplifier.net/resolve?scope=nhsd.assets.stu3@1.7.0&canonical=https://fhir.nhs.uk/STU3/ValueSet/ITK-InfAcknowledgement-1
Url https://fhir.nhs.uk/STU3/ValueSet/ITK-InfAcknowledgement-1
Version 1.1.0
Status draft
Date 2017-12-21T11:09:00+00:00
Name ITK Infrastructure Acknowledgement
Experimental False
Authority hl7
Description A valueset to describe the ITK infrastructure acknowledgements returned to the sender.
Copyright Copyright ©2017 NHS Digital

Resources that use this resource

No resources found


Resources that this resource uses

CodeSystem
https://fhir.nhs.uk/STU3/CodeSystem/ITK-Acknowledgement-1 ITK Acknowledgement


Source

{
  "resourceType" : "ValueSet",
  "id" : "ITK-InfAcknowledgement-1",
  "meta" : {
    "lastUpdated" : "2017-12-21T11:09:00+00:00"
  },
  "url" : "https://fhir.nhs.uk/STU3/ValueSet/ITK-InfAcknowledgement-1",
  "version" : "1.1.0",
  "name" : "ITK Infrastructure Acknowledgement",
  "status" : "draft",
  "date" : "2017-12-21T11:09:00+00:00",
  "publisher" : "NHS Digital",
  "contact" : [
    {
      "name" : "Interoperability Team",
      "telecom" : [
        {
          "system" : "email",
          "value" : "interoperabilityteam@nhs.net",
          "use" : "work"
        }
      ]
    }
  ],
  "description" : "A valueset to describe the ITK infrastructure acknowledgements returned to the sender.",
  "copyright" : "Copyright ©2017 NHS Digital",
  "compose" : {
    "include" : [
      {
        "system" : "https://fhir.nhs.uk/STU3/CodeSystem/ITK-Acknowledgement-1",
        "concept" : [
          {
            "code" : "51001",
            "display" : "Success"
          },
          {
            "code" : "51002",
            "display" : "Unrecognised Recipient Person"
          },
          {
            "code" : "51003",
            "display" : "Unrecognised Sender"
          },
          {
            "code" : "51004",
            "display" : "Non Approved file type received as an attachment"
          },
          {
            "code" : "51005",
            "display" : "Payload validation failure"
          },
          {
            "code" : "51006",
            "display" : "Document content validation failure"
          },
          {
            "code" : "51007",
            "display" : "Attachment file type invalid"
          },
          {
            "code" : "51008",
            "display" : "Unrecognised Recipient Organisation"
          },
          {
            "code" : "51009",
            "display" : "Unauthorised Sender"
          },
          {
            "code" : "51010",
            "display" : "Duplicate Message received"
          },
          {
            "code" : "51011",
            "display" : "Duplicate Document received"
          },
          {
            "code" : "51012",
            "display" : "Service failure"
          },
          {
            "code" : "51013",
            "display" : "Unreadable message received"
          },
          {
            "code" : "RC001",
            "display" : "Handling Specification Error"
          },
          {
            "code" : "RC002",
            "display" : "Business Acknowledgement - Processing Error"
          },
          {
            "code" : "RC003",
            "display" : "Infrastructure Acknowledgement - Processing Error"
          },
          {
            "code" : "RC004",
            "display" : "Message Definition – Processing Error"
          },
          {
            "code" : "RC005",
            "display" : "Priority - Processing Error"
          },
          {
            "code" : "RC006",
            "display" : "Sender Reference - Processing Error"
          },
          {
            "code" : "RC999",
            "display" : "Handling Specification Business Rule Error"
          }
        ]
      }
    ]
  },
  "text" : {
  }
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.